@bblommers I am having some issue with some of the endpoints. On line 147 of moto/kafka/responses.py, it is correctly printing (and returning) the response but the response isn't correct in the tests. I think it's a URL issues but not sure. Any ideas?

Hi @jamarcelin! It looks like some of the response-keys simply need to be lowercased. For example:

diff --git a/moto/kafka/models.py b/moto/kafka/models.py
index 5cd36741d..e2973d5f8 100644
--- a/moto/kafka/models.py
+++ b/moto/kafka/models.py
@@ -231,11 +231,11 @@ class KafkaBackend(BaseBackend):
     ):
         cluster_info_list = [
             {
-                "ClusterArn": cluster.arn,
-                "ClusterName": cluster.cluster_name,
-                "ClusterType": cluster.cluster_type,
-                "State": cluster.state,
-                "CreationTime": cluster.creation_time,
+                "clusterArn": cluster.arn,
+                "clusterName": cluster.cluster_name,
+                "clusterType": cluster.cluster_type,
+                "state": cluster.state,
+                "creationTime": cluster.creation_time,
             }
             for cluster in self.clusters.values()
         ]

That change ensures that the list_clusters_v2()-method call succeeds in the test_create_cluster_v2(). I imagine that the other failures/tests have similar problems/solutions, but I haven't tested that.

This is the first thing I tried, and it happened to work - just because I have run into this problem in the past. The botocore spec is always good place to confirm things like this though, as you can see that they lowercase all locationName's:

https://github.com/boto/botocore/blob/cacd0e9fdba71d1f976069a072576ad74b888bea/botocore/data/kafka/2018-11-14/service-2.json#L2429

@bblommers Gotcha, thanks for the help! I fixed the tests and made some changes. The linter is having an issue with broker_node_group_info from FakeKafkaCluster. Any idea how to resolve this?

Hi @jamarcelin! You can run ruff format moto/kafka to fix that. I've pushed a fix for now + some typing fixes - I'll leave the test failures to you 🙂

@bblommers Test should be fixed now, just waiting on check to complete. Thanks again!

@bblommers Hey, sorry to keep pinging, it seems the tests are failing in server mode? Is this caused by an issue with the urls?

Codecov Report

Attention: Patch coverage is 97.29730% with 5 lines in your changes missing coverage. Please review.

Project coverage is 94.60%. Comparing base (1291c55) to head (5a3e308).
Report is 13 commits behind head on master.

@@           Coverage Diff            @@
##           master    #8381    +/-   ##
========================================
  Coverage   94.59%   94.60%            
========================================
  Files        1159     1163     +4     
  Lines      101394   101632   +238     
========================================
+ Hits        95911    96144   +233     
- Misses       5483     5488     +5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@jamarcelin I pushed a commit to fix the urls. They have ARNs in them, which contain forward slashes.

Awesome! Thanks for the help! This looks good to merge to me. Also, is there a specific cadence for releases? Or is there anyway to trigger a release?

Also, is there a specific cadence for releases? Or is there anyway to trigger a release?

I try to do them every two weeks - the next one should come this weekend. 🙂